-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(page): Handle submit and "back" functionality #3678
Conversation
e315223
to
43e9455
Compare
8049191
to
0e6b5df
Compare
Removed vultr server and associated DNS entries |
previousValues: getPreviouslySubmittedData(props), | ||
}); | ||
|
||
const onSubmit: FormikConfig<SchemaUserData>["onSubmit"] = (data) => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As with the List
component, we're preversing both forms of data here as opposed to writing to and parsing from a single format.
This seems like an ok approach, especially as it's following an established pattern?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
By "preversing both forms of data" you're referring to defaultPassportData
and flattenedData
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, that's right. We could parse/map/serialise both into a single structure and then unpack that on "back" navigation, but I'm proposing we allow both just now 👍
a119474
to
ed12378
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Data structures make sense to me here, agree List is right precedent/pattern to follow here 👍
What does this PR do?
main
commit across projects